home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
bbs
/
fate_v10.zip
/
SYSOP.DOC
< prev
next >
Wrap
Text File
|
1996-05-22
|
11KB
|
226 lines
FATE Version 1.0 -- Program & Design by Charles Culver & Eric Cameron
WARNING
-------
This game may contain some violence and vulgar language so if you
find any of these offensive, or think you may, then do NOT play the
game!
DISCLAIMER
The author has taken every precaution to insure that no harm
or damage will occur on computer systems operating this package.
Nevertheless, the author shall NOT be held liable for whatever
may happen on your computer system or to any computer systems
which connects to your own as a result of operating this package.
The user assumes full responsibility for the correct operation of
this software package, whether harm or damage results from software
error, hardware malfunction, or operator error. NO warranties are
offered, expressly stated or implied, including without limitation
or restriction any warranties of operation for a particular purpose
and/or merchantability. If you do not agree with this then do NOT
use this program.
REQUIREMENTS:
------------
FILES=10 (or more) in your config.sys file
ANSI.SYS must also be in your config.sys file
A FOSSIL is NOT required to run the game, but it is suggested
Installation
------------
1. Create a directory for the game:
example: "c:\pcb\doors\fate_v1
2. Make sure that ALL files included in this ZIP file
are moved into that directory.
3. Type "DDSETUP.EXE" and hit the enter key. The first thing it
will ask you is what the name of the CTL file is. Type in
"FATE.CTL" and then proceed to the other settings. After
you are done the FATE.CTL file should be correctly configured.
If all else fails - try the one I use on MY BBS (Sample.CTL).
Where to put this file?
Put this file wherever you are running the game executable file
from.
4. In order to run the game program online the following
parameters may be used.
"/Bxxxxx" This tells GAME.EXE to lock its baud rate at
xxxxx. In order to get the most efficiency out of a high speed
error correcting modem (9600 baud or above), you may lock the baud
rate to a speed higher than what the caller is actually using.
By locking the baud to say 38,400, the modem can compress text data
that is being sent and achieve a baud rate much higher than the
actual transmission rate.
This will lock the baud rate at the same value for all nodes that
use this command line. If you perfer a more selective way to lock
baud use 'LOCKBAUD' command in the GAME.CTL file.
"/Cx" (where x is 1..4) This specifies a comport number.
Some bbs software does not create door information files (dropfiles)
that contain the comport number. If your bbs does have a comport
listed in the dropfile then there is no need for this parameter.
The default is comport 0, local mode.
"/E" - Expanded Memory Specification If your machine has over one
megabyte of memory, then you may have some available. GAME.EXE can
utilize EMS to improve game performance and reduce conventional
memory requirements.
This command will tell GAME.EXE to use EMS memory to hold its
overlay buffer. Otherwise disc area may be used to hold this buffer.
This needs a memory manager and when enabled and is compatible with
DESQview. Default is NOT to use available EMS.
"/L" This tells GAME.EXE to load up in LOCAL mode.
This is good for testing or when a sysop just wants to "try out" the
door without messing with his BBS setup. The "/L" mode will ask the
user for his name and run the door in local mode.
"/Nx" (where x is 1..9) This specifies a "node number".
Some bbs software support multinode environments in which you must
know the node number of the drop file to use. For example, RBBS-PC
uses DORINFOx.DEF. If you specified "/N2" then GAME.EXE would use
DORINFO2.DEF.
"/Mx" (where x is up to 2 filename acceptable characters)
Used to specify one of Multiple control files. If you have created
more than one GAME.CTL file (GAME1.CTL, GAME2.CTL, etc.) for each
node or network PC then you can select the one you want by using
the /M parm.
Example: "/M2" will force GAME.EXE to use GAME2.ctl.
"/Pyyy" This specifies the path to the drop files.
For example, "/PC:\WILDCAT\WCWORK\NODE1" would tell GAME.EXE to
look for the drop file in C:\WILDCAT\WCWORK\NODE1. If this is left
out the program assumes the drop file is local.
"/R" To force local RIP for the sysop. Used only if the program
has RipLink built in and the door supports RIP. Use AFTER the
/L parameter if you are using the door in local mode.
"/V" This command will tell GAME.EXE not to show any display
on the local screen. Only a colored screen and a message will be
displayed. The cursor will not move as it will be turned off.
Saves a little processing on multi-tasking systems.
"/W" This flags the program that a network is present even
though no multitaskers are detected. This is useful if the door is
run on a network such as Novell that doesn't use multitaskers.
COMMON ERRORS
003 File path not found. Check to make sure the game
directory is correctly named as GAMEDIR.
201 Files not found. Check to make sure that all required
games files are in the GAMEDIR directory.
8. Install the door into your BBS software (see your BBS
software documentation for more information). A batch file is
normally used to do this. To run the program just have your
batch file change to the GAMEDIR directory and run GAME.EXE -
Thats all there is to it! A batch file sample is included to
help you run the game. It is included with the game for editing
and your use.
RESTRICTIONS ON THE UNREGISTERED GAME
-------------------------------------
Until the game is registered the following restrictions are
in effect:
a. You can NOT buy the guard a Goldschlager.
b. You can NOT go past level 7
c. Registering the game disables both of the above.
d. Once you are registered any future updates can be obtained
free through my BBS.
WHAT TO DO IF THERE ARE PROBLEMS
--------------------------------
Every effort is made to ensure that the game runs correctly
before it leaves my BBS as Shareware. If you are experiencing
problems please do the following BEFORE calling me:
1. Read ALL the SYSOP.DOC to ensure you have setup the program
and have met all the program requirements.
2. Use the B4UASK.DOC as a checklist to ensure that you have
not done anything wrong.
"Corrupted" data files
----------------------
It is possible that something could happen to your game
data file. A power outage, game crash, or other event could
damage the data files. If you get one of these messages,
then the best thing